From: matrss Date: Mon, 13 Oct 2025 12:28:11 +0000 (+0000) Subject: (no commit message) X-Git-Tag: archive/raspbian/10.20251029-1+rpi1~1^2~3^2~17^2~2 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https://%22Program/%22http:/www.example.com/cgi/%22https:/%22Program?a=commitdiff_plain;h=16c347c60d3c2f9c210457a377367c39408035f9;p=git-annex.git --- diff --git a/doc/forum/Git-annex_in___34__AGit-Flow__34__.mdwn b/doc/forum/Git-annex_in___34__AGit-Flow__34__.mdwn new file mode 100644 index 0000000000..f1662dc3a0 --- /dev/null +++ b/doc/forum/Git-annex_in___34__AGit-Flow__34__.mdwn @@ -0,0 +1,18 @@ +Forgejo supports ["AGit-Flow"](https://forgejo.org/docs/latest/user/agit-support/) to make pull requests without requiring a user to fork a repository first. This is achieved by having a sort of branch namespace `refs/for//` which can be pushed to by users that only have read access to the repository. This will open a PR from this branch to the named target branch. + +There are efforts in upstream Forgejo to make this a more prominent alternative to forking for contributions: . + +I am wondering how git-annex could best fit into this flow. I would like to be able to create PRs containing annexed files on Forgejo-aneksajo in this way (tracking issue on the Forgejo-aneksajo side: ). Obviously annexed objects copied to the Forgejo-aneksajo instance via this path should only be available in the context of that PR in some way. + +The fundamental issue seems to be that annexed objects always belong to the entire repository, and are not scoped to any branch. + +I've thought of these options so far: +- Provide a "per PR special remote" that the creator of the PR could push annexed files to. This would require the user to configure an additional remote, which the AGit-Flow tries to avoid for plain-git contributions. +- A per-user special remote that is assumed to contain the annexed files for all of the users AGit-PRs. If git recognizes remote configs in the users' global git config then it could be possible to get away with configuring things once, but I am not sure of the behavior of git in that case. +- Allow read-only users to have append-only access to the annex. This must at least be limited to secure hashes though, and there are implications of DoS by malicious users filling disk space / quotas. + +Worth it to note that AGit-Flow already works for Contributors with write access, since they can write to the annex freely anyway. + +Do you have any other ideas on how git-annex could be used in this workflow? + +[[!tag projects/INM7]]